@dantmnf hello, thanks

Can you clarify a bit what this endpoint does ? cause based on other user's test it seem to be backlight brightness toggle (i might be wrong tho). What does OOBE stands for ?

I think this should be a "feature" to indicate the system is starting by turning keyboard backlight on and off.

The term OOBE (out-of-box experience) is taken from Linux asus-wmi source, seems to be also reverse-engineered.

The two affected models AFAIK are on shining new platform (AMD Strix Point / Intel Lunar Lake), I'm not sure if Asus repurposed the endpoint in this generation.

@dantmnf ok, then it could be that I have misunderstood sense of this in a first place.

So to summarize

Setting 0x0005002F to 1 - enables normal backlight operation and setting it to 0 - makes keyboard blink ?

setting it to 0 - makes keyboard blink ?

I haven't checked if this will make keyboard blink again - obviously not a feature wanted for daily use, but it do have value 0 after system startup.

@dantmnf but can you set it to 0 and check what effect it has ? Does keyboard start blinking ?

Ok I will check it when the device comes back to me - maybe a few days later

@dantmnf but can you set it to 0 and check what effect it has ? Does keyboard start blinking ?

It has no effect. The keyboard won't start blinking again until a full shutdown and restart.

@dantmnf ok, great. Then I have misinterpreted sense of this endpoint based on on feedback of other users.

Since OOBE resets on reboot, i assume it will also reset on hibernate / wakeup from it. So it makes sense to run it every time device changes power mode.

I have added OOBE command to TUF Keyboard Power method instead (responsible for backlight zones in different states and running every time power is changed)

534dc3d

Can you check if this build works properly ?
GHelper.zip

i assume it will also reset on hibernate / wakeup from it.

You're right. I didn't think about the hibernate case.

Can you check if this build works properly ?

It works well.

@dantmnf ok! then i assume it's fine as is now? Thanks for spotting and clarifying!

I have a new Vivobook S16 and have this issue when turning my laptop on. Do I need to trigger something in GHelper to stop the rainbow puke or is this just supposed to work out of the box with GHelper?

Side note - thanks for adding my laptop to OLED list.

@memnon8711 you don't need to do anything, as far as you use latest release - it will set this command as soon as app starts. You can verify it by checking if record mentioning VIVO OOBE exists in %appdata%\GHelper\log.txt after app start.

I do see the line "VIVO OOBE = 1 : OK" in the log file. I just notice the rainbow RGB comes one when I turn on the computer and I have to cycle through the brightness to turn it off. Small nit.

@memnon8711 can you check if this build behaves differently ?
GHelper.zip

That worked. The rainbow RGB was displaying when it booted up, but once Windows and GHelper loaded, it turned off the lighting and went back to the state I had it in previously. Thanks for the quick response.

@memnon8711 ok, great . I just swapped OOBE command and initial backlight setting that app sets